first draft of merging connectors content #484
Conversation
georgewallace
force-pushed
the
connectors
branch
from
d7c96a2 to
7f0fd0d
Compare
georgewallace
force-pushed
the
connectors
branch
from
1bc48f5 to
73436ce
Compare
|
@shainaraskas I think this is good for a v1. let me know what you think. |
There was a problem hiding this comment.
95% there. just some questions re: applies_to, some big images, and some questions re: things that might not apply to serverless. generally, I see the following things as possible serverless red flags:
- settings
written.like.thisand passed in config files/panels - 3p integrations like terraform
- APIs
deploy-manage/manage-connectors.md
Outdated
| ## Connector networking configuration [_connector_networking_configuration] | ||
|
|
||
| Use the [action configuration settings](https://www.elastic.co/guide/en/kibana/current/alert-action-settings-kb.html#action-settings) to customize connector networking configurations, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use `xpack.actions.customHostSettings` to set per-host configurations. |
There was a problem hiding this comment.
this doesn't apply to serverless - what do serverless users do?
| :::{image} ../images/kibana-connector-select-type.png | ||
| :alt: Connector select type | ||
| :class: screenshot | ||
| ::: |
There was a problem hiding this comment.
this image is vv large - can we use the width attribute to resize?
|
|
||
| For out-of-the-box and standardized connectors, refer to [preconfigured connectors](https://www.elastic.co/guide/en/kibana/current/pre-configured-connectors.html). | ||
|
|
||
| ::::{tip} |
There was a problem hiding this comment.
this feels like it isn't applicable to serverless either
There was a problem hiding this comment.
You are correct. I took a stab at calling out both preconfigured connectors and the Terraform provider in a singular note. Not sure if this is ok with our current guidelines.
deploy-manage/manage-connectors.md
Outdated
| :::{image} ../images/kibana-connectors-import-banner.png | ||
| :alt: Connectors import banner | ||
| :class: screenshot | ||
| ::: |
There was a problem hiding this comment.
this image is even more large
consider the value of the images: do we need them?
deploy-manage/manage-connectors.md
Outdated
| ## Monitoring connectors [monitoring-connectors] | ||
|
|
||
| **This page is a work in progress.** The documentation team is working to combine content pulled from the following pages: | ||
| The [Task Manager health API](../deploy-manage/monitor/kibana-task-manager-health-monitoring.md) helps you understand the performance of all tasks in your environment. However, if connectors fail to run, they will report as successful to Task Manager. The failure stats will not accurately depict the performance of connectors. |
There was a problem hiding this comment.
this API isn't available in serverless.
deploy-manage/manage-connectors.md
Outdated
|
|
||
| * [/raw-migrated-files/kibana/kibana/action-types.md](/raw-migrated-files/kibana/kibana/action-types.md) | ||
| * [/raw-migrated-files/docs-content/serverless/action-connectors.md](/raw-migrated-files/docs-content/serverless/action-connectors.md) | ||
| For more information on connector successes and failures, refer to the [Event log index](../explore-analyze/alerts-cases/alerts/event-log-index.md). |
There was a problem hiding this comment.
not sure if this applies (or not sure how to access without the API)
Co-authored-by: shainaraskas <[email protected]>
| :class: screenshot | ||
| ::: | ||
|
|
||
| ## Monitoring connectors [monitoring-connectors] |
There was a problem hiding this comment.
@shainaraskas I took a stab at going into a bit more details here to talk about monitor in both cases with the Task manager health API and with the event log. Since you can use the event log in both
Co-authored-by: shainaraskas <[email protected]>
!2 participants
No description provided.